-
Notifications
You must be signed in to change notification settings - Fork 32
✨ Add a Distributed Task Queue (using Celery) (🏗️ ⚠️DEVOPS) #7214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ Add a Distributed Task Queue (using Celery) (🏗️ ⚠️DEVOPS) #7214
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #7214 +/- ##
==========================================
+ Coverage 86.30% 87.25% +0.95%
==========================================
Files 1671 1720 +49
Lines 64728 66572 +1844
Branches 1048 1157 +109
==========================================
+ Hits 55866 58090 +2224
+ Misses 8563 8151 -412
- Partials 299 331 +32
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry for forgetting to unblock, this is all good, thank you very much! 💪
…o/osparc-simcore into add-distributed-task-queue
…o/osparc-simcore into add-distributed-task-queue
|
* Add sto-worker simcore service Related PR: ITISFoundation/osparc-simcore#7214 * Tighten CPU resource constraints

What do these changes do?
Introduce a Distributed Task Queue (using Celery). On the first iteration it will be used by Storage service for file compression.
The Storage now works on 2 modes:
STANDARDandWORKER.In the
STANDARDmode, the service uses Celery to submit tasks and get progress/results.In the
WORKERmode, it is executed as Celery worker (with FastAPI intitialized) and it is responsible for tasks execution.Related issue/s
storagedummy rpc endpoints for zipping #7202How to test
Dev-ops checklist